Interchangeable device components

ABSTRACT

Implementations described herein provide a component system that reconfigures interchangeable computing device components based on a current state of the computing device. The current state of the computing device is determined based on a hardware configuration of the device, a shell configuration describing software and firmware of the device, and/or context information describing a relationship between the device and its surrounding environment. Based on the current state of the computing device, an output is determined that specifies interchangeable components are to be activated and deactivated. The output is useable to reconfigure individual computing device functionalities, control a manner in which applications execute on the computing device, and adapt the computing device to its current state.

RELATED APPLICATION

This application claims priority under 35 U.S.C. § 119(e) to U.S.Provisional Patent Application No. 62/505,942, filed on May 14, 2017entitled “Multi-Display Device Techniques,” the entire disclosure ofwhich is incorporated by reference in its entirety. Further, thisapplication is a continuation of and further claims priority to U.S.Non-Provisional patent application Ser. No. 15/834,343 entitled“INTERCHANGEABLE DEVICE COMPONENTS”, filed on Dec. 7, 2017, which ishereby incorporated by reference herein, in its entirety.

BACKGROUND

Computing device functionalities are often designed for specificdevices, such that similar functionalities operate differently ondifferent devices. For example, functionality for rendering an operatingsystem user interface may result in different user interfaces whenimplemented by different device types, such as a mobile device and atelevision device. Conventional techniques for reconfiguring afunctionality from its default state for a given device often requiremanual installation and rebooting in order for the reconfiguration totake effect. Thus, conventional techniques for reconfiguring computingdevice functionalities are often unable to adapt to changes.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Implementations described herein provide a component system forconfiguring individual functionalities of a computing device based on acurrent state of the computing device. Individual computing devicefunctionalities (e.g., an operating system, input/output mechanisms,system services, and so forth) are associated with interchangeablecomponents that can be separately applied to reconfigure operation ofthe functionalities. In at least one implementation, the functionalitiesare reconfigurable based on a state of the computing device.Accordingly, a state of the computing device is determined based on ahardware configuration available to the device, a shell configurationdescribing software and firmware available to the device, contextinformation describing a relationship between the device and itssurrounding environment, and so forth. Based on the state of thecomputing device, a configuration output is determined that specifiesinterchangeable components that are to be activated and/or deactivated.The configuration output is useable for various purposes, such as toreconfigure individual computing device functionalities, control amanner in which applications execute on the computing device, and adaptthe computing device to its current state.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different instances in thedescription and the figures may indicate similar or identical items.

FIG. 1 is an illustration of an environment in an example implementationthat is operable to employ techniques discussed herein in accordancewith one or more implementations.

FIG. 2 depicts an example implementation scenario for interchangeabledevice components in accordance with one or more implementations.

FIG. 3 depicts an example implementation scenario for generating anoutput for interchangeable device components in accordance with one ormore implementations.

FIG. 4 depicts an example implementation scenario for configuring aclient device with interchangeable device components in accordance withone or more implementations.

FIG. 5 depicts an example implementation scenario for configuringinterchangeable device components based on a number of device users inaccordance with one or more implementations.

FIG. 6 depicts an example implementation scenario for configuringinterchangeable device components based on a device posture change inaccordance with one or more implementations.

FIG. 7 depicts an example implementation scenario for configuringinterchangeable device components based on a combination of devices inaccordance with one or more implementations.

FIG. 8 is a flow diagram that describes steps in a method for generatingan output based on a hardware state, a shell state, and a context stateof a client device in accordance with one or more implementations.

FIG. 9 is a flow diagram that describes steps in a method forconfiguring a client device in response to detecting a change in statein accordance with one or more implementations.

FIG. 10 is a flow diagram that describes steps in a method for executingan application using interchangeable device components in accordancewith one or more implementations.

FIG. 11 illustrates an example system and computing device as describedwith reference to FIG. 1, which are configured to implementimplementations of techniques described herein.

DETAILED DESCRIPTION

Implementations described herein enable configuration of a computingdevice, such as through activation and deactivation of interchangeablecomponents based on a current state of the computing device. Generally,individual interchangeable components are useable to configurefunctionality of the computing device and are modular in the sense thatthey can be applied to a range of different device types and devicestates. Accordingly, the computing device can be reconfigured byactivating and deactivating various components in order to adapt to acurrent state. Similarly, a manner in which applications execute on thecomputing device can be dictated by representing the computing device asa set of selected components.

For instance, consider a scenario where a first user is interacting witha mobile device via touch inputs to an integrated touchscreen. Usingtechniques described herein, the mobile device is configured based onits current state. As described herein, a current state for the mobiledevice can be defined based on information describing a hardware state,a shell state, and a context state of the mobile device. A change instate may occur, for example, when the mobile device is passed from thefirst user to a second, visually impaired user. This change in state canbe communicated to the mobile device based on updated contextinformation identifying the second user as being visually impaired andbeing the current primary user of the device. Based on this updatedcontext information, the mobile device's touchscreen can be reconfiguredin real time to adapt to the current device state. For instance, acomponent corresponding to visual output functionality of thetouchscreen can be disabled and a component corresponding tofunctionality of a screen narrator can be enabled based on the contextinformation indicating that the second user is visually impaired.Alternatively, a component corresponding to functionality of thetouchscreen can be replaced with a different component that correspondsto a large text functionality of the touchscreen when the contextinformation indicates that the second user suffers from presbyopia.

Implementations are also operable to cause an application to execute ona computing device in a certain manner by representing the computingdevice to the application as being a set of interchangeable components.For instance, an application may be designed to have a first userexperience while executing on a device with an integrated camera and asecond, different user experience while executing on a device with nointegrated camera. The first user experience, for example, may include adisplay area with an icon for accessing camera functionality while thesecond user experience includes an icon for accessing a freeform drawingprogram in the same display area. As an example, consider a scenariowhere the application is executing on a device with an integratedcamera, but a user's hand is covering the integrated camera. Usingtechniques described herein, the device may be represented to theapplication as a set of components that excludes the integrated camera,thereby causing the application execute as if no integrated cameraexists on the device and display the freeform drawing icon instead ofthe camera icon.

Thus, techniques described herein enable configuring a computing deviceand its individual functionalities, such as during runtime, based on astate of the computing device. The described techniques may improvedevice performance in a number of ways, such as by enabling certaindevice components to be disabled and thus reduce power consumptionand/or increase battery charge life, by reducing processor load byreducing a number of active components and thus data from the componentsthat requires processing, and so forth.

FIG. 1 is an illustration of an environment 100 in an exampleimplementation that is operable to employ techniques for configuringinterchangeable components of a client device based on a state of theclient device. Environment 100 includes a client device 102 which can beembodied as any suitable device such as, by way of example and notlimitation, a smartphone, a tablet computer, a portable computer (e.g.,a laptop), a desktop computer, a wearable device, a device integratedinto clothing, and so forth. In at least some implementations, theclient device 102 represents a smart appliance, such as an Internet ofThings (“IoT”) device. Thus, the client device 102 may range from asystem with significant processing power, to a lightweight device withminimal processing power. One of a variety of different examples of theclient device 102 is shown and described below in FIG. 11.

The client device 102 includes a variety of different functionalitiesthat enable various activities and tasks to be performed. For instance,the client device 102 includes an operating system 104, applications106, and a communication module 108. Generally, the operating system 104is representative of functionality for abstracting various systemcomponents of the client device 102, such as hardware, kernel-levelmodules and services, and so forth. The operating system 104, forinstance, can abstract various components (e.g., hardware, software, andfirmware) of the client device 102 to the applications 106 to enableinteraction between the components and the applications 106.

The applications 106 represents functionalities for performing differenttasks via the client device 102. Examples of the applications 106include a word processing application, a spreadsheet application, a webbrowser, a gaming application, and so forth. The applications 106 may beinstalled locally on the client device 102 to be executed via a localruntime environment, and/or may represent portals to remotefunctionality, such as cloud-based services, web apps, and so forth.Thus, the applications 106 may take a variety of forms, such aslocally-executed code, portals to remotely hosted services, and soforth.

The communication module 108 is representative of functionality forenabling the client device 102 to communicate over wired and/or wirelessconnections. For instance, the communication module 108 representshardware and logic for communication via a variety of different wiredand/or wireless technologies and protocols.

The client device 102 further includes a display device 110, an outputmodule 112, and an input module 114. The display device 110 generallyrepresents functionality for visual output for the client device 102.The display device 110, for instance, represents an instance of anoutput mechanism supported by the output module 112. Additionally, insome implementations the display device 110 represents functionality forreceiving various types of input, such as touch input, pen input, and soforth. The display device 110, for instance, represents an instance ofan input mechanism supported by the input module 114, such that thedisplay device 110 is configured to receive touch based inputs from auser's hand, a stylus, and so forth.

The output module 112 is representative of functionality for generatingdata for output via one or more output mechanisms of the client device102, such as generating audio data for output at a speaker of the clientdevice, generating visual data for output at the display device 110,generating haptic feedback for output via the display device 110, and soon. The output module 112, for instance, includes a rendering enginethat can process and output data for display on the display device 110.

The input module 114 is representative of functionality for receivinginput to the client device 102 via one or more input mechanisms of theclient device. The input module 114, for instance, includes an inputmapping system that maps input signals to various functionalities of theclient device 102 based on a current state of the client device. Forexample, the input module 114 may employ target disambiguationtechniques for input signals generated by touch input devices todetermine an intended input location based on received touch input in amanner that accounts for variations in user input.

The input module 114, for instance, may perform input targetdisambiguation with a relatively small factor for input variation whenan adult user is interacting with the client device 102. Usingtechniques described herein, the input module 114 may be dynamicallyreconfigured to perform target disambiguation with a relatively largefactor for input variation when a child user is interacting with theclient device 102. In this manner, the input module 114 can beconfigured to alter a user experience for an operating system,application, module, and so forth, based on a hardware state, a shellstate, or a context state for the client device 102.

In order to assist in determining a current state of the client device102, the client device 102 additionally includes memory/storage 116storing device type information 118 as well as user profile information120. The device type information 118 describes the client device 102,such as by a serial number, a manufacturer, a model, a hardwarespecification, a software specification, combinations thereof, and soforth. Alternatively or additionally, the device type information 118describes current and historical activity for the operating system 104,applications 106, communication module 108, output module 112, and/orinput module 114. Generally, the user profile information 120 describesone or more user profiles associated with the client device. Forinstance, a user profile can include information describing a particularuser, such as a user's age, a user's accessibility needs, and so forth.Alternatively or additionally, the user profile information 120 includeshistorical data describing a manner in which the particular userinteracts with the client device 102, such as voice training data,gesture training data, recorded input data, and so forth.

The client device 102 additionally includes a component system 122,which is representative of functionality for determining a current stateof a the client device, based on a hardware state, a shell state, and acontext state of the client device, and generating an output based onthe current state. For instance, the component system 122 includes ahardware state module 124, a shell state module 126, and a context statemodule 128. As described herein, the hardware state module 124 isrepresentative of functionality for monitoring a hardware state of theclient device 102, which describes one or more hardware devices that areavailable to the client device. For instance, a current hardware stateof the client device 102 may be defined by one or more input and outputdevices that are available to the client device, a hardwarespecification of the client device, and/or hardware specifications ofone or more devices connected to the client device. In someimplementations, the hardware state module 124 determines a hardwarestate of the client device 102 based on the device type information 118.

The shell state module 126 is representative of functionality formonitoring a shell state of the client device 102, which describessoftware and firmware available to the client device. For instance, theshell state of the client device 102 may describe versions of theoperating system 104, the applications 106, the communication module108, the output module 112, and/or the input module 114 that areavailable for use by the client device 102.

The context state module 128 is representative of functionality formonitoring a context state of the client device 102, which describes theclient device 102 in relation to a surrounding environment (e.g., inrelation to a user of the device and how the user is using the device).For instance, the context state of the client device 102 can bedescribed by data or signals associated with a user's grip on thedevice, a relative position of the device, sound, behavioral data, HallEffect, user settings, visual data, external connections, combinationsthereof, and so forth. This is not an exhaustive list, and is onlyrepresentative of various information that can be used to describe acontext state of the client device 102, as described in further detailbelow.

The component system 122 is operable to configure the client device 102to adapt to a current state of the device, which includes at least oneof a hardware state, a shell state, or a context state of the device. Inthis manner, user experiences associated with the operating system 104,the applications 106, and so forth can be dynamically adapted to changesin context.

For instance, the environment 100 includes an example configuration 130,an example configuration 132, and an example configuration 134, whicheach represent configurations of the client device 102 that are adaptedbased on one or more of a hardware state, a shell state, or a contextstate of the client device 102. The example configuration 130 isrepresentative of a scenario where a child user is interacting with theclient device 102. In the example configuration 130, an overall userexperience for the client device 102 is simplified, such as byrepresenting functionality of the operating system 104, the applications106, and so forth, using large icons for display instead of a desktopuser experience with small icons, operating system chrome, and so forth.In some implementations, simplifying the overall user experience for theclient device 102 is performed by reducing a number of interchangeablecomponents running in parallel on the client device 102, as described infurther detail below. As described herein, interchangeable componentsrunning parallel on the client device 102 also refers to interchangeablecomponents that are executing concurrently on the client device 102.

The example configuration 132 is representative of a scenario wheremultiple users are simultaneously interacting with the client device102. In the example configuration 132, two users are illustrated assimultaneously interacting with opposite sides of the client device 102.Thus, in order to provide simultaneous access to functionalities of theclient device 102, the example configuration 132 includes two userinterfaces with duplicate instances of the operating system 104, theapplications 106, and so forth, which are simultaneously accessible bythe two users.

In some implementations, configuring the client device 102 toaccommodate multiple users is performed by creating duplicate instancesof one or more components running on the client device and thusincreasing a number of interchangeable components running in parallel onthe client device. As described herein, a duplicate instance of a clientdevice component can function independently with respect to the clientdevice component from which it was generated. Thus, a first user caninteract with the operating system 104 via client device 102 while asecond user simultaneously interacts with the operating system 104 in adifferent manner, without affecting the other user's experience.Alternatively, the duplicate instances of the client device componentscan simultaneously perform the same functionality.

The example configuration 134 is representative of a scenario where thedisplay device 110 is disabled based on a current state of the clientdevice 102, which can be defined by one or more of a hardware state, ashell state, or a context state of the client device 102. For instance,the example configuration 134 may be representative of a scenario wherethe client device 102 is communicatively coupled to an automobile whilethe automobile is moving. In this scenario, a component corresponding tofunctionality of the display device 110 is disabled to reduce potentialdistractions that may otherwise occur from a user looking at the displaydevice 110 while driving. Continuing this example scenario, if theclient device 102 is connected to automobile hardware devices, such asan integrated display device, microphone, speaker system, and so forth,input and output to the client device 102 may be redirected to theautomobile hardware devices rather than input and output mechanisms ofthe client device 102.

Alternatively or additionally, the example configuration 134 may berepresentative of a scenario where the client device 102 is configuredfor a user with vision accessibility needs. In this example scenario, ifa visually impaired user is interacting with the client device 102,visual output at the display device 110 may be ineffective incommunicating information. Thus, the display device 110 may be disabledby deactivating a component corresponding to functionality of thedisplay device 110. Instead, a component corresponding to functionalityof a screen narrator may be activated to configure the client device 102for the visually impaired user. Thus, using techniques described herein,the client device 102 can be adapted to different configurations basedon a current state of the client device.

Having described an example environment in which techniques describedherein may operate, consider now a discussion of some exampleimplementation scenarios for configuring a client device using acomponent system in accordance with one or more implementations. Theimplementation scenarios may be implemented in the environment 100described above, the system 1100 of FIG. 11, and/or any other suitableenvironment.

FIG. 2 depicts an example implementation scenario 200 for enablingcomponentized, modular functionality of the client device 102. Thescenario 200 shows that different functionalities of the client device102 are associated with different interchangeable components, such asthe operating system 104, the output module 112, the input module 114,and sensors 206. Using techniques described herein, each component canbe separately applied to reconfigure operation of a respectivefunctionality. Thus, each functionality of the client device 102 can bereconfigured with a respective component and based on a variety ofdifferent criteria, such as one or more of a hardware state, a shellstate, or a context state of the client device 102.

For instance, components can be interchanged by activating ordeactivating individual components based on a change in the hardwarestate, a shell state, or a context state of the client device 102. Forinstance, components can be interchanged based on a change in deviceposition and/or posture of the client device 102, based on a change inenvironmental factors (e.g., light level, time of day, temperature, andso forth), based on a change in how a user is holding the client device102 (e.g., a change in grip), a change in user identity for a user thatis interacting with the client device 102, and so forth.

Consider, for example, that the components 104 a-104 c areinterchangeable to reconfigure the operating system 104. For instance,when the client device 102 detects that a child user is interacting withthe client device 102, one of the components 104 a-104 c can be selectedthat reconfigures the operating system 104 to provide a simplified userexperience. As an example, a component 104 b can be selected thatdisplays a user interface for the operating system 104 as a collectionof enlarged icons. Conversely, a component 104 a can be selected upondetecting that an adult user is interacting with the client device 102to provide a desktop user interface for the operating system 104 thatenables the adult user to access additional functionality not enabled bythe component 104 b selected for a child user.

According to some implementations, an application 106 can be handled asone of the components 104 a-104 c of the operating system 104. Forinstance, when the client device 102 is powered on and the operatingsystem 104 is booted, the application 106 can be automatically launchedand executed on the client device 102 without requiring explicit userinput to launch the application 106. Thus, the application 106 can bebound to the operating system 104, such as based on explicit userpreferences and/or detected hardware and context factors. For instance,when the operating system 104 is booted and the application 106 islaunched, the status of the application 106 on the client device 102 canbe indicated as a system component rather than a separate, executingapplication.

As another example, consider that the components 112 a-112 c areinterchangeable to configure the output module 112. For instance, whenthe client device 102 pairs with another device, such as with anautomobile, one of the components 112 a-112 c can be selected thatreconfigures the output module 112 to utilize an output mechanism of theautomobile rather than an output mechanism of the client device 102. Asan example, a component 112 c can be selected that causes audio outputfrom the client device 102 to emit from an automobile speaker ratherthan a speaker integrated into the client device 102. As an alternativeor additional example, a component 112 b can be deactivated when theclient device 102 pairs with the automobile to deactivate the displaydevice 110 while the client device 102 and the automobile are paired andwhen the automobile is moving.

As an alternative or additional example, components 114 a-114 c areinterchangeable to reconfigure the input module 114. For instance, whenthe client device 102 detects that a user may have an impairment due toa physical and/or environmental condition, one of the components 114a-114 c can be selected that reconfigures the input module 114 toaccount for the impairment. As an example, upon detecting that avisually impaired user is interacting with the device, a component 114 acan be selected that enlarges visual input functionality that isdisplayed by the client device 102, such as to better enable the user tointeract with an intended input target.

In addition or alternatively to selecting a component based on useridentity, a component may be selected based on a change in environmentalfactors. For instance, a component 114 a can be interchanged with acomponent 114 c in response to detecting that the client device 102 isbeing used in a low-light environmental setting, such as to reduce adisplay brightness of visual input functionality that is displayed bythe client device 102.

In the example implementation scenario 200, the client device 102 isillustrated as including input mechanisms 202. The input mechanisms 202generally represent different functionalities for receiving input to theclient device 102, and include a digitizer 204, one or more sensors 206,touch input devices 208, and analog input devices 210. Examples of theinput mechanisms 202 thus include gesture-sensitive sensors and devices(e.g., such as touch-based sensors and movement-tracking sensors (e.g.,camera-based)), a mouse, a keyboard, a stylus, a touch pad,accelerometers, a microphone with accompanying voice recognitionsoftware, and so forth. The input mechanisms 202 may be separate orintegral with the display device 110, with integral examples includinggesture-sensitive displays with integrated touch-sensitive ormotion-sensitive sensors.

Each input mechanism 202 may be associated with interchangeablecomponents to reconfigure the input mechanism. For instance, thecomponents 206 a-206 c are interchangeable to reconfigure the sensors206. In an example scenario, sensors 206 may include an image sensor,where a component 206 a is representative of a configuration for theimage sensor in normal lighting conditions and a component 206 b isrepresentative of a configuration for the image sensor in low-lightconditions. Continuing this example scenario, a component 206 c isrepresentative of a configuration in which the image sensor isunavailable, such as when the image sensor is disabled or when the imagesensor is covered by a user's grip on the client device 102.

Based on a current state of the client device 102, the component system122 configures the image sensor by activating or deactivating differentones of the components 206 a-206 c at runtime. For instance, thecomponent system 122 may activate a component 206 c in response to adetermination by the context state module 128 that a user's finger iscovering a lens of the camera. Likewise, the component system 122 mayselectively activate a component 206 a and a component 206 b based on adetected time of day, an amount of light received by the image sensor,and so forth. Additionally or alternatively, a component may be disabledbased on a current state of the client device 102. For instance,component 206 a and component 206 b may be disabled when a battery levelof the client device drops below a threshold to conserve battery power.

In at least some implementations, different components can be obtainedfrom a network resource, such as from a component store 212 over anetwork 214. The component store 212, for instance, can enable varioustypes and combinations of interchangeable components to be obtained bythe client device 102.

FIG. 3 depicts an example implementation scenario 300 for generating anoutput based on one or more of a device's hardware state, a shell state,or a context state in accordance with one or more implementations. Thescenario 300 includes the component system 122 and the hardware statemodule 124, shell state module 126, and context state module 128, asintroduced in FIG. 1. The component system 122 additionally includes acomponent configuration module 302, which is configured to receivehardware information 304, shell information 306, and context information308. Based on at least one of the hardware information 304, shellinformation 306, or context information 308, the component configurationmodule 302 generates a configuration output 310 in order to dynamicallyadapt the client device 102 based on a state of the device.

The hardware information 304 describes a hardware state of the clientdevice 102, such as a manufacturer of the device, a make of the device,a model of the device, a description of hardware components installed onthe device, and so forth. In some implementations, the hardware statemodule 124 determines the hardware information 304 based on the devicetype information 118, as introduced in FIG. 1. The hardware information304 also describes input and output devices that are available for useby the client device 102, such as the display device 110 and the inputmechanisms 202.

In some implementations, the hardware information 304 describes ahardware configuration of a computing device that is communicativelyconnected to the client device 102. For instance, in an implementationwhere the client device 102 is paired with one or more differentcomputing devices, the hardware information 304 includes informationdescribing hardware configurations of each of the different computingdevices, as well as information describing input and output devices thatare available for use by the client device 102 via the differentcomputing devices.

As an example, the hardware information 304 may specify that the clientdevice 102 is a desktop computing device with an Brand X ver. 1.5processor, keyboard, mouse, and camera input mechanisms 202, two displaymonitors, and an integrated speaker system. The hardware information 304may additionally specify that the client device 102 is paired with amobile computing device via Bluetooth, and that the mobile computingdevice includes a microphone, touchscreen and camera input mechanisms,and an integrated display device. Thus, the hardware information 304 isuseable to describe a hardware state of a client device, such that thecomponent system 122 can specifically determine a current hardwareconfiguration and hardware components available to the client device 102at runtime.

The shell information 306 describes a shell state of the client device102, such as software and firmware available to the client device 102.In some implementations, the shell state module 126 determines the shellinformation 306 based on the device type information 118, as introducedin FIG. 1. The shell information 306, for instance, describes a currentversion of the operating system 104, the applications 106, thecommunication module 108, the output module 112, and/or the input module114 that are available for use by the client device 102.

For example, developers often design applications to have different userexperiences on different device types. As such, an application 106 maybe developed to include a desktop version designed for implementation ona desktop computing device and a mobile version designed forimplementation on a mobile device. The shell information 306 can thusspecify that a component for a desktop version of an application 106 iscurrently installed on client device 102, but that a mobile version ofthe application 106 is additionally available, such as from thecomponent store 212 via the network 214, as introduced in FIG. 2.

In some implementations, the shell information 306 describes a shellstate of a computing device that is communicatively coupled to theclient device 102. For instance, in an implementation where the clientdevice 102 is paired with a mobile device, the shell information 306includes information describing software and firmware installed on boththe client device 102 as well as the mobile device. As an example, theshell information 306 may specify that the client device 102 is runninga third build of a Brand Y operating system and that the mobile deviceis running a fourth build of a Brand Y operating system.

Alternatively or additionally, the shell information 306 may describeone or more applications 106 and their respective versions installed onthe client device 102 as well as applications and their respectiveversions installed on the mobile device. Thus, the shell information isuseable to describe a shell state of the client device 102, such thatthe component system 122 can specifically determine a current softwareand firmware configuration of the client device 102, as well as softwareand firmware configurations that are available to the client device atruntime.

The context information 308 describes a current context state of theclient device 102, such as information describing the client device 102in relation to a user of the device, how the user is using the device,and so forth. Thus, context information 308 can include any type of dataor signals that are useable to describe a current state of the clientdevice 102 in relation to its surrounding environment. For instance, thecontext information 308 can include data or signals associated with oneor more of a user's grip on the device, a relative position of thedevice, sound detected in a surrounding environment, behavioral data,Hall Effect, user settings, visual data, external connections, and soon. This list of context information is not exhaustive and thus not tobe construed as limiting with respect to examples of context information308, as described in further detail below.

One example of context information 308 is information describing auser's grip on the client device 102 during operation of the device. Forinstance, information describing the user's grip can be detected by oneor more of the input mechanisms 202, such as by the sensors 206, asintroduced in FIG. 2. As an example, a user's grip on the client device102 can be detected by capacitive strips on the outside of the clientdevice and/or separate capacitive sensors on the rear exterior of theclient device 102. Alternatively or additionally, the user's grip can bedetected based on a capacitance of a display surface of the clientdevice 102, such as display device 110. Information describing the gripcan specify whether the user has fingers wrapped around the clientdevice 102, which hand (e.g., left or right hand) the user is using thehold the client device 102, in which of a variety of different posturesthe user is holding the device, and so on. Accordingly, contextinformation 308 describing a user's grip indicates how the user isholding the client device 102, which is useable to infer how the userintends to use the device.

Another example of context information 308 is a relative position of theclient device 102, such as in relation to a user of the client device102, in relation to the ground, and/or in relation to another referencelocation. For example, information describing a relative position of theclient device 102 can indicate whether the client device is resting on asurface or whether the display device 110 is facing the user. Inimplementations, information describing a relative position of theclient device 102 can be used to determine a current posture of theclient device 102. Various types of sensors, such as sensors 206, can beemployed to determine a relative position of the client device,including cameras, accelerometers, magnetometers, and so on. Thus,context information 308 may be used to describe the client device 102relative to its surrounding environment.

Another example of context information 308 is a sound detected by theclient device 102, such as to enable a user to initiate device commandsaudibly. For example, one or more audio sensors can be utilized todetect spoken commands by a user of the client device 102 and anapproximate direction and/or distance of the audio source (e.g., theuser) relative to the client device 102. In this manner, the contextinformation 308 can describe that the user is interacting with theclient device 102 via audible commands rather than through touch inputdevices 208, as introduced in FIG. 2. The sound may also be used todescribe a noise level of the environment surrounding client device 102.For instance, the context information 308 may describe whether theclient device 102 is being operated in a noisy environment, a quietenvironment, and so forth. Thus, context information 308 may be used todescribe sounds detected by the client device 102.

Another example of context information 308 is behavioral data, which isrepresentative of how a user tends to interact with the client device102 or particular applications 106 executed on the client device 102.For example, when using the client device 102 in a configuration withtwo or more display devices, the user may tend to run certainapplications on a left display device and other applications on a rightdisplay device. In another example, the user may generally take notes ona right side of the display device 110 because the user is right-handed.As a result, the context information 308 may be used to generate aconfiguration output 310 that biases displayed information to a leftside of the display device 110, such that the user's right hand does notobscure displayed information. In some implementations, the contextstate module 128 ascertains behavioral data from the user profileinformation 120, as introduced in FIG. 1.

There are many different reasons why a user may have particularpreferences related to how the user tends to use the client device 102.Behavioral data included in the context information 308, although it maynot explicitly represent preferences in the form of settings, thusincludes behavioral information describing how the user uses the device.In this manner, using context information 308, some user actions can beanticipated. For example, when a notetaking application is launched, thecomponent system 122 can use the context information 308 to generate theconfiguration output 310 to launch the notetaking application via aparticular display device in a scenario where the hardware information304 indicates that the client device is connected to multiple displaydevices. Continuing this example, the particular display device isselected because the component system 122 is aware that the user has apreference for viewing the notetaking application via the particulardisplay device and that the user likely intends that particular displaydevice to be the primary display.

As another example of context information 308, information describing aHall Effect may be included, which refers to the production of apotential difference across an electrical conductor when a magneticfield is applied in a direction perpendicular to that of the flow ofcurrent. Hall Effect sensors (e.g., magnetometers) can detect magneticfields in close proximity. In implementations, context informationdescribing a Hall Effect can be used to detect changes in posture of theclient device 102, such as when the client device is opened from aclosed posture to an open posture, or vice versa. Thus, based on thisHall Effect described in context information 308, the component system122 can be used to deactivate display devices when the client device 102is manipulated into a closed posture, to activate one or more displaydevices when the client device 102 is manipulated into an open posture,and so forth.

Alternatively or additionally, the context information 308 may includeinformation describing one or more user settings that indicate how auser tends to use the client device 102, such as with respect toergonomics-related user settings. Ergonomics-related user settings canbe used to further refine the configuration output 310 based on acurrent context state of the client device 102 (e.g., left/righthandedness can be used to predict a likely flip direction, or hand sizeinformation can be used for more reliable grip detection). By includinginformation associated with user settings, the context information 308can be used to predict which direction the user is going to turn thedevice when the user's intent is to flip the client device 102 over.

Configuring the client device 102 based on context information 308 canbe useful in differentiating situations that are similar in nature, suchas a first situation where the user rotates the device 180 degrees tosee the reverse side, versus a second situation where the user rotatesthe device 180 degrees to show a friend content displayed via theprimary display. In the first situation, the configuration output 310can cause a primary display of the client device 102 to be changed to adisplay device on a reverse side of the client device 102 opposite theuser, to enable the user to view content via the reverse side.Conversely, in the second situation, the configuration output 310 canmaintain the primary display while the primary display is temporarilyfacing away from the user in order to show displayed content to thefriend, which accounts for the likely intent of then turning the deviceback around for the user to continue viewing the original primarydisplay. Accordingly, the context information 308 is useable by thecomponent system 122 to disambiguate similar situations.

Alternatively or additionally, user settings included in the contextinformation 308 can include hand dimensions representing a size andshape of the user's hand(s) grasping the client device 102. The handdimensions can then be used in conjunction with other contextinformation 308, such as for more reliable grip detection. Similarly,the hand dimensions can be used as a manner to identify the user, theuser's handedness (left or right), a shape of the user's fingers, and soon. This information can allow the system to more robustly detect howthe user is holding the device, which can then be used to generate anconfiguration output 310 that accounts for how the user likely intendsto interact with the client device 102, based on a current context stateof the device.

As another example, context information 308 may describe visual data,which includes visual information captured via an input device, such asa camera of the client device 102. For example, the client device 102can include multiple integrated cameras, such as front-facing and/orrear-facing cameras. Visual data may thus be obtained from the cameras(e.g., image and/or video data) to detect whether a correspondingsurface of the client device 102 is facing a user. In implementations,the visual data can further describe a particular portion of a displaydevice at which a user is looking. Alternatively or additionally, visualdata may describe that a camera is currently covered by a user's grip onthe client device, and the configuration output 310 may be generated toindicate that the covered camera is disabled or otherwise unavailablefor use by the applications 106. Thus, the context information 308 candescribe a context state of the client device 102 based on visual datadescribing an environment surrounding the client device.

As an additional example, context information 308 may includeinformation describing one or more current connections between theclient device 102 and one or more external computing devices. Forexample, the client device 102 can be connected to one or more externaldisplays to display content, such as to give a presentation to a groupof people. In this example, attention is given to the external devicerather than the client device 102. Thus, the configuration output 310may be generated to cause display of presentation information on theexternal device while displaying a user's presentation notes on adisplay integrated into the client device 102.

As another example, the context information 308 can include informationdescribing an executing application 106 or the operating system 104itself. Based on particular occurrences, the context information 308 canthus be used to anticipate a user's intended interaction with the clientdevice 102. For example, assuming the client device 102 has the abilityto switch between front and rear-facing cameras, the context information308 may specify that a user has selected an in-application command or anoperating system-related command that expresses the user's intent ofperforming a next action. This context information 308 can thus be usedto generate an configuration output 310 that adjusts one or moredetection parameters to dynamically adapt to a user's interaction withthe client device, based on a current task and the indication of asubsequent task. Accordingly, the context information 308 isrepresentative of a wide variety of data and signals that can areuseable to define a current context state of the client device 102.

The component configuration module 302 is thus configured to dynamicallyadapt the client device 102 based on one or more of a hardware state, ashell state, or a context state of the client device, as described bythe hardware information 304, shell information 306, and contextinformation 308 via configuration output 310. In implementations, theconfiguration output 310 includes instructions for activating ordeactivating one or more components of the client device 102, such asthe various components introduced in FIG. 2.

For instance, the shell state of the client device 102 may describeversions of the operating system 104, the applications 106, thecommunication module 108, the output module 112, and/or the input module114 that are available for use by the client device.

Having described some example types of hardware information 304, shellinformation 306, and context information 308, consider now some exampleconfigurations of the client device 102 in accordance with one or moreimplementations.

FIG. 4 depicts an example implementation scenario 400 for configuringthe client device 102 based on at least one of a hardware state, a shellstate, or a context state of the client device 102. The scenario 400 isrepresentative of functionality provided by the component system 122 toconfigure the client device 102 according to a configuration 402 and aconfiguration 404. Using techniques described herein, the componentsystem 122 causes the client device 102 to dynamically transitionbetween the configuration 402 and the configuration 404 by determiningat least one of a hardware state, a shell state, or a context state ofthe client device and generating an configuration output 310, such asillustrated in FIG. 3.

In the scenario 400, the configuration 402 represents a configurationfor the client device 102 that provides a relatively complex userexperience, contrasted against the configuration 404, which represents aconfiguration for the client device 102 that provides a relativelysimple user experience. In some implementations, the relative complexityor simplicity of a user experience is defined based on a number ofinterchangeable components running in parallel on the client device 102.For example, the configuration 402 may represent an instance where theclient device 102 is running a greater number of components in parallelthan a number of components running in parallel for the configuration404. Alternatively, the configuration 404 may represent an instancewhere the client device 102 is running an equal or greater number ofcomponents in parallel than a number of components running in parallelfor the configuration 402, such as to address user accessibility needs.

In the scenario 400, configuration 402 is illustrated as a windoweddesktop display configuration for the client device 102. In animplementation, the component system 122 may determine that an adultuser 406 is interacting with the client device through contextinformation 308 received from the context state module 128. In someimplementations, the component system 122 determines that the adult user406 is interacting with the client device 102 based on user profileinformation 120, as introduced in FIG. 1. Alternatively or additionally,the component system 122 may determine that the client device 102 iscommunicatively coupled with mouse and keyboard input mechanisms 408,which may be representative of analog input devices 210, as introducedin FIG. 2. In some implementations, the component system 122 determinesthat the client device 102 is communicatively coupled with mouse andkeyboard input mechanisms 408 based on hardware information 304 receivedfrom the hardware state module 124.

The component system 122 may thus determine from the received hardwareinformation 304 that the client device 102 is in a current hardwarestate similar to that of a desktop computing device and determine fromthe received context information 308 that the client device 102 is beingused by an adult user 406. Based on this information describing ahardware state, a shell state, and a context state of the client device102, the component system 122 determines that the relatively complexconfiguration 402 is appropriate for the current state of the clientdevice 102. Accordingly, the component system 122 configures the clientdevice in the configuration 402 to provide the adult user 406 with asuite of functionality offered by the operating system 104 andapplications 106. Furthermore, the component system 122 configures theclient device 102 in a manner that optimizes the client device forinteraction via keyboard and mouse input mechanisms 408. Inimplementations, the component system 122 configures the client device102 in the configuration 402 by generating an configuration output 310that specifies a set of client device components that provide theconfiguration 402.

In contrast to the relatively complex configuration 402, the componentsystem 122 can determine that the client device 102 should bereconfigured to the relatively simple configuration 404, based on achange in state to the client device 102. For example, the componentsystem 122 may determine that the adult user 406 is no longerinteracting with the client device 102 and that a child user 410 iscurrently interacting with the client device 102. The component system122 may determine that the child user 410 is interacting with the clientdevice 102 based on context information 308 received from the contextstate module 128. For instance, the context state module 128 may monitorinput received at one or more of the input mechanisms 202 of the clientdevice 102 and determine that touch input received from a hand of theadult user 406 has changed to touch input received from a smaller handof the child user 410.

In response to determining this change in context state for the clientdevice 102, the component system 122 generates an configuration output310 that causes the client device to transition from the configuration402 to the configuration 404 to provide a simplified user experience forthe child user 410. This transition from the configuration 402 to theconfiguration 404 may include selectively activating a different set ofinterchangeable components and may also include changing a number ofcomponents running in parallel on the client device 102. In someimplementations, the component system 122 identifies that theconfiguration 404 is associated with the child user 410 based on userprofile information 120 for the child user 410, as introduced in FIG. 1.

For instance, profile information 120 for the child user 410 mayindicate that the child user 410 is only permitted to access a certainsubset of applications 106 via a simplified user interface thatrepresents the subset of applications as the large icons 414 a-414 f.The user experience of configuration 404 is further simplified byremoving operating system chrome, which refers to portions of a userinterface that are part of the operating system 104 rather than any ofapplications 106. Thus, by detecting a change in state where the devicetransitions from an adult to a child user, the component system 122 canselectively activate client device components to seamlessly adapt theuser experience associated with the client device 102 at runtime.Because the client device 102 can be reconfigured at runtime, thereconfiguration can be performed independent of manual user input, suchas without requiring the adult user 406 to manually sign out and thechild user 410 to manually sign in.

Alternatively or additionally, the component system 122 may detect achange in hardware state for the client device 102, such as adisconnection between the client device 102 and the mouse and keyboardinput mechanisms 408. Upon detecting the change in hardware state, thecomponent system 122 can ascertain that the client device 102 may becontrolled using voice commands 412. For instance, the hardware statemodule 124 may determine that a microphone input mechanism 202 isavailable when the mouse and keyboard input mechanisms 408 aredisconnected from the client device 102. In response to thisdetermination, the component system 122 may generate an configurationoutput 310 that causes the client device 102 to transition fromprocessing input signals received at the mouse and keyboard inputmechanisms 408 to processing input signals received via the voicecommands 412. In some implementations, this transition includesdeactivating client device components corresponding to the mouse andkeyboard input mechanisms 408 and activating one or more devicecomponents that enable the client device 102 to be controlled usingvoice commands 412.

Although the scenario 400 includes configurations 402 and 404,techniques described herein enable the component system 122 to adapt theclient device 102 among a continuum of different configurations in orderto dynamically adjust to a current state of the client device 102. Forexample, in a scenario where the keyboard and mouse mechanisms 408 aredisconnected from the client device 102 and the adult user 406 isinteracting with the client device 102, an output may be generated thatconfigures the client device 102 in a third configuration. In thisexample third configuration, the client device 102 may provide a hybriduser experience that combines different aspects of the configuration 402and the configuration 404, such as where functionality of the operatingsystem 104 and applications 106 are displayed in a windowed desktoplayout that can be interacted with using voice commands 412.

Thus, upon detecting a change to one or more of a hardware state, ashell state, or a context state of the client device 102, the componentsystem 122 generates an output that specifies a subset of client devicecomponents to be activated, such as a subset of the componentsillustrated in FIG. 2. In this manner, the component system 122dynamically adapts the client device 102 during runtime to account forstate changes, such as to account for user accessibility needs, changesin available hardware, and so forth.

FIG. 5 depicts an example implementation scenario 500 for configuringclient device 102 based on at least one of a hardware state, a shellstate, or a context state of the client device 102. The scenario 500 isrepresentative of functionality provided by the component system 122, asintroduced above.

The scenario 500 illustrates that the client device 102 is configurableaccording to a configuration 502. In the configuration 502, a singleuser 504 is illustrated as interacting with the client device 102. Theclient device 102 may be configured in the configuration 502, forexample, based on context information 308 that indicates only one useris interacting with the client device 102. The client device 102 isillustrated as including display device 110, which in this exampleincludes two separate display devices 110 a and 110 b.

In the configuration 502, the display device 110 includes a display of awindowed desktop user interface for an operating system 104 and one ormore applications 106, spanning across display devices 110 a and 110 b.For instance, the configuration 502 includes a display of a window 506 aat display device 110 a, which may correspond to a designated displayarea for displaying operating system 104 information, application 106information, and so on. The configuration 502 additionally includes adisplay of a window 506 b at display device 110 b, which may correspondto a designated display area for displaying operating system 104information, application 106 information, and so on. The configuration502 additionally includes a display of operating system chrome 508,which is represented as a taskbar displayed at a side of the displaydevice 110 proximate to the user 504, spanning across the displaydevices 110 a and 110 b. Further, the configuration 502 includes adisplay of one or more icons 510, which are representative of additionalclient device functionality, such as an application shortcut, systemcontrols, and so forth.

A display orientation and layout of the windows 506 a and 506 b,operating system chrome 508, and one or more icons 510 can thus becontrolled by the component system 122, based on shell information 306describing available components for the operating system 104 and one ormore applications 106. Alternatively or additionally, the displayorientations and layouts can be controlled by the component system 122based on hardware information 304 describing various hardware componentsavailable for activation at the client device 102. Thus, theconfiguration 502 represents a display configuration for the clientdevice 102 based on a hardware state of the device, a shell state of thedevice, and a context state of the device, where a single user 504 isinteracting with the client device 102.

The lower portion of the scenario 500 illustrates that, based on achange in device context, the client device 102 is reconfiguredaccording to a configuration 512. For instance, the display device 110is illustrated as outputting a display for the configuration 512 wherethe user 504 and an additional user 514 are simultaneously interactingwith the client device 102. The client device 102 may be configured inthe configuration 512, for example, based on context information 308that indicates a context state where multiple users are interacting withthe device.

In the configuration 512, the display devices 110 a and 110 b areconfigured to display two separate user interfaces, such as to create aduplicate instance of the interface illustrated in the configuration 502for the additional user 514. For instance, the configuration 512includes a first instance of the user interface 516 for the user 504 atdisplay device 110 a and a second instance of the user interface 518 forthe additional user 514 at display device 110 b. The component system122 is configured to generate multiple instances of a user interface, oruser experience, provided by the client device 102 by creating multipleinstances of client device components and running the multiple instancesof client device components in parallel while the additional user 514 isinteracting with the client device. This is represented by the first andsecond instances of the user interface 516 and 518 each including thewindows 506 a and 506 b, operating system chrome 508, and one or moreicons 510, as introduced in the configuration 502.

The component system 122 is additionally configured to adjust a displayposition and orientation of the windows 506 a and 506 b, operatingsystem chrome 508, and one or more icons 510 when transitioning betweenthe configurations 502 and 512. For instance, the component system 122adjusts a display position of the windows 506 a and 506 b to display onthe user interface 516, in order to maintain a user experience for theuser 504 and accommodate the additional user 514.

In some implementations, the windows 506 a and 506 b, operating systemchrome 508, and icon 510 are each representative of a different clientdevice component. For example, the operating system chrome 508 may berepresentative of a component 104 a, as introduced in FIG. 2.Accordingly, the component system 122 is configured to generate a newinstance of the component 104 a based on context information 308 thatindicates the additional user 514's interaction with the client device102. The component system 122 is additionally configured to activate thenew instance of the component 104 a so that the user 504 and additionaluser 514 can each interact with the operating system chrome 508. Thecomponent system 122 can similarly generate and activate duplicateinstances of client device components corresponding to the windows 506 aand 506 b and one or more icons 510 to accommodate multiple users at theclient device 102.

Although described in the context of two users, the component system 122is configured to generate duplicate instances of one or more devicecomponents to accommodate any number of users simultaneously interactingwith the client device 102. Likewise, in response to detecting a changein context state for the client device 102 where fewer users areinteracting with the device, the component system 122 is configured todeactivate duplicate instances of the client device components, suchthat the client device 102 activates a number of components based on anumber of users currently acting with the device.

A duplicate instance of a client device component can perform the sameor different functionality as the instance of the client devicecomponent from which it was generated. For instance, assume that theoperating system chrome 508 in the user interface 516 represents aninstance of component 104 a and that the operating system chrome 508 inthe user interface 518 represents a duplicate instance of component 104a. Based on a current state of the client device 102, the componentsystem 122 may cause the two instances of component 104 a tosimultaneously perform the same operations, or may allow for theinstance of component 104 a and the duplicate instance of component 104a to be simultaneously used for different functionality.

For example, if user 504 interacts with the operating system chrome 508in user interface 516 to access a start menu for the operating system104, the component system 122 can cause the operating system chrome 508in user interface 518 to simultaneously access the same start menu forthe operating system 104. In this manner, the component system 122 canactivate and run additional components in parallel to effectivelyreplicate display areas at convenient viewing angles for respectiveusers of the client device 102. Alternatively or additionally, thecomponent system 122 can enable the additional user 514 to access searchfunctionality of the operating system chrome 508 in user interface 518while the user 504 accesses a start menu of the operating system chrome508 in user interface 516. Thus, a duplicate instance of a client devicecomponent can perform the same or different functionality as the clientdevice component from which the duplicate instance was created.

To do so, upon detecting a change to one or more of a hardware state, ashell state, or a context state of the client device 102, the componentsystem 122 generates an output that either increases or decreases anumber of client device components running in parallel. In this manner,the component system 122 dynamically adapts the client device duringruntime to account for device state changes.

FIG. 6 depicts an example implementation scenario 600 for configuringclient device 102 based on at least one of a hardware state, a shellstate, or a context state of the client device 102. The scenario 600 isrepresentative of functionality provided by the component system 122, asintroduced above. The client device 102 is illustrated as includingdisplay device 110, which comprises two separate display devices 110 cand 110 d. Using techniques described herein, the component system 122selectively controls the display device 110 by dynamically transitioningbetween a configuration 602 and a configuration 604 by determining atleast one of a hardware state, a shell state, or a context state of theclient device and generating an configuration output 310, as discussedwith reference to FIG. 3.

In the scenario 600, the configuration 602 represents an orientation ofthe client device 102 where the separate display devices 110 c and 110 dare oriented to face a relatively similar direction. For instance, theconfiguration 602 is representative of a scenario where a user of thedevice has oriented the display devices 110 c and 110 d about a hinge606, such that the display devices 110 c and 110 d are both facing theuser. Based on context information 308 describing the currentorientation of the client device 102, the component system 122 maydetermine that only a single user is interacting with the client device102 and cause the display device 110 to output information in a mannersimilar to the single user configuration 502, as described with respectto FIG. 5.

In the configuration 604, the client device 102 is illustrated as beingoriented about the hinge 606, such that the display devices 110 c and110 d are facing opposite one another. Using techniques describedherein, the component system 122 is configured to monitor the clientdevice 102 and determine that a change in context state for the clientdevice occurs between the configuration 602 and 604. For instance, thecomponent system 122 may ascertain, based on context information 308,that the display device 110 c is no longer facing a user of the clientdevice 102 and deactivate one or more client device components used tocontrol display device 110 c. Thus, the component system 122 isconfigured to alter a number of client device components running inparallel based on a change in posture of the client device 102.

In an alternative example, the component system 122 may determine, basedon context information 308, that the user of the client device 102 hasmanipulated the client device from the configuration 602 to theconfiguration 604 in order to enable another user to simultaneouslyinteract with the client device 102. For instance, the context statemodule 128 may detect the change in client device 102 posture and detectthat the display device 110 c is facing a different user in theconfiguration 604. Continuing this example, the component system 122 mayconfigure the client device 102 for simultaneous interaction by multipleusers, such as by generating duplicate instances of client devicecomponents and simultaneously displaying the duplicate instances atdisplay devices 110 c and 110 d. Thus, the component system 122 can maycause the display device 110 c to display the user interface 518 andcause the display device 110 d to display the user interface 516, asdescribed above with respect to FIG. 5.

Thus, upon detecting a change to one or more of a hardware state, ashell state, or a context state of the client device 102, the componentsystem 122 generates an output that specifies a subset of client devicecomponents to be activated, such as a subset of the componentsintroduced in FIG. 2. In this manner, the component system 122dynamically adapts the client device 102 during runtime to account fordevice state changes.

FIG. 7 depicts an example implementation scenario 700 for configuringclient device 102 based on at least one of a hardware state, a shellstate, or a context state of the client device. The scenario 700 isrepresentative of functionality provided by the component system 122, asintroduced above. In the scenario 700, hardware, shell, and contextstate changes are described in the context of a client deviceestablishing or terminating connections to a different computing device.Using techniques described herein, the component system 122 dynamicallyactivates and/or deactivates various components of the client devicebased on components that are available for use by the client device,given a current state of the client device 102. In some implementations,the component system 122 activates and deactivates individual componentsof the client device 102 via the configuration output 310 of FIG. 3.

The scenario 700 includes a client device 702 that is communicativelyconnectable to and disconnectable from a client device 704. The clientdevices 702, 704, for instance, represent different instances of theclient device 102. In this particular example, the client devices 702,704 are connected to each other such that the client devices 702, 704function as a single integrated instance of the client device 102. Theclient devices 702, 704, for example, can exchange data and distributevarious computing-related tasks between the two devices to present aunified user experience. The client devices 702, 704 can be connected invarious ways, such as via a physical connection that enables physicaland signal connectivity between the devices. One example of such aconnection is the hinge 606 described with reference to FIG. 6.Alternatively or additionally, the client devices 702, 704 can beinterconnected via a wireless connection that enables data and/or powerto be wirelessly communicated between the client devices 702, 704.

The client devices 702, 704 are also able to function independently viathe their own separate integrated functionality. The client devices 702,704, for example, can be disconnected to represent separate functionalinstances of the client device 102. As further described below, each ofthe client devices 702, 704 includes separate functionality that isindependently operable to provide different computing experiences, suchas separate display devices, separate processors, separate operatingsystems, and so forth. In the following discussion, the client devices702, 704 will be discussed in the context of single instance of theclient device 102.

Further to the scenario 700, the client device 702 includes a camera706, an audio sensor 708, and a display device 710, each of which may beassociated with one or more interchangeable components, as indicated bycomponents 706 a-706 c, 706 a, 706 b, and 710 a. Client device 702additionally includes a processing system 712 with an associatedcomponent 712 a, and an operating system 714 with an associatedcomponent 714 a.

Further, the client device 704 includes a camera 716, an audio sensor718, and a display device 720, each of which may be associated with oneor more interchangeable components, as indicated by components 716 a-716c, 718 a, 718 b, and 720 a. Client device 704 additionally includes aprocessing system 722 with an associated component 722 a and anoperating system 724 with an associated component 724 b.

In an example implementation, the individual components 706 a-706 crepresent different functionalities of the camera 706. For instance,component 706 a may represent functionality of an image processor,component 706 b may represent functionality of a lens, and component 706c may represent functionality of an image sensor, which collectiverepresent functionality of the camera 706 for client device 702.Further, component 708 a may represent functionality of an analog todigital converter (ADC) and component 708 b may represent functionalityof a microphone, which together represent functionality of the audiosensor 708 for client device 702.

Continuing this example implementation, component 716 a may representfunctionality of an image processor, component 716 b may representfunctionality of a lens, and component 716 c may represent functionalityof an image sensor, which collective represent functionality of thecamera 716 for client device 704. Further to this exampleimplementation, component 718 a may represent functionality of an ADCand component 718 b may represent functionality of a microphone, whichtogether represent functionality of the audio sensor 718 for clientdevice 704. Although client devices 702 and 704 are described as havingsimilar components for their respective cameras 706 and 716 and audiosensors 708 and 718, this example implementation is not intended to belimiting. For instance, client device 702 may be associated withinterchangeable components that are different from interchangeablecomponents of the client device 704, such that no interchangeablecomponent from client device 702 overlaps with an interchangeablecomponent of client device 704.

Using techniques described herein, the component system 122 configuresthe client device 102 by activating a subset of components from theclient devices 702, 704. In the example scenario 700, the client device102 includes an operating system 104, the functionality of which isconfigured by the component system 122 through the selection andactivation of component 724 a. In implementations, the component 724 amay be selected for configuring the operating system 104 based on shellinformation 306. For instance, the component system 122 may ascertainfrom shell information 306 that the component 724 a corresponds to aversion of the operating system 104 that has been updated more recentlythan a version of the operating system corresponding to component 714 a.Alternatively or in addition to shell information 306, the component 724a may be selected and activated based on at least one of hardwareinformation 304 or context information 308.

Continuing the example implementation 700, the client device 102includes the output module 112, the functionality of which is configuredby the component system 122 through selection and activation ofcomponents 710 a and 720 a. Thus, in the example implementation 700, theclient device 102 is configured to leverage both the display device 710of client device 702 and the display device 720 of client device 704 tofunction as output mechanisms for client device 102. In this manner, thecomponent system 122 dynamically configures the output module 112 basedon hardware information specifying that display devices 710 and 720 areconnected and available for use by the client device 102. Alternativelyor in addition to hardware information 308, the components 710 a and 720a may be selected and activated based on at least one of shellinformation 306 or context information 308.

The client device additionally includes the input module 114,functionality of which is configured by the component system 122 throughselection and activation of components 716 a, 706 b, 706 c, 718 a, and718 b. Thus, in the example implementation 700, the client device 102 isconfigured to include a camera that incorporates the image processor ofcamera 716, as represented by component 716 a, and the lens and imagesensor of camera 706, as represented by components 706 b and 706 c. Thecomponent system 122, for instance, may determine from contextinformation 308 that the client device 102 is in a low-light setting andthat optimum image quality can be obtained by using a combination ofinterchangeable components from cameras 706 and 716.

Further, the client device 102 is configured to include audio sensor718, as represented by the components 718 a and 718 b. In someimplementations, selection and activation of the components for inputmodule 114 is performed based on one or more of a shell state, ahardware state, or a context state of the client device 102. Forinstance, shell information 306 may describe that the audio sensor 708has enhanced sound sensing performance in comparison to the audio sensor718, but context information 308 may describe that a user's current gripon the client device 702 is covering the audio sensor 708. Accordingly,the component system 122 is configured to select components of the audiosensor 718 based on the current context of the client device 102.

Further to the scenario 700, the client device 102 includes a processingsystem 726, the functionality of which is configured by the componentsystem 122 through selection and activation of components 712 a and 722a. Thus, in the example implementation 700, the client device 102 isconfigured to leverage both processing systems of client devices 702 and704 to execute functionality of the client device 102. In this manner,the component system 122 dynamically configures the processing system726 based on hardware information 304, which specifies that theprocessing systems 712 and 722 are connected and available for use bythe client device 102. Alternatively or in addition to hardwareinformation 308, the components 712 a and 722 a may be selected andactivated based on at least one of shell information 306 or contextinformation 308.

Accordingly, techniques described herein enable dynamic configuration ofa device that can adapt to changes of a hardware state, a shell state,and/or a context state of the device. Similarly, techniques describedherein can be used to dictate a manner in which an application interactswith a computing device, even if the application is not developed to beaware of a current state of the computing device on which it isexecuting.

Having described some example implementation scenarios, consider nowsome example procedures for interchangeable device components inaccordance with one or more implementations. Generally, the proceduresmay be implemented in the environment 100 described above, the system1100 of FIG. 11, and/or any other suitable environment. The procedures,for example, describe example ways for implementing various aspects ofthe scenarios described above. In at least some implementations, stepsdescribed for the various procedures are performed automatically andindependent of user interaction.

FIG. 8 is a flow diagram that describes steps in an example method forgenerating an output based on one or more or a hardware state, a shellstate, or a context state of a client device in accordance with one ormore implementations.

Step 800 determines a hardware state of a client device. The hardwarestate module 124, for instance, determines hardware information 304 thatdescribes a hardware configuration of the client device 102, one or moreinput mechanisms connected to the client device 102, and one or moreoutput mechanisms connected to the client device 102. For example, thehardware information 304 includes information that describes the inputmechanisms 202 of the client device 102, such as the digitizer 204,sensors 206, sensor components 206 a-206 c, touch input devices 208,analog input devices 210, keyboard and mouse input mechanisms 408, andvoice control 412 as described above and illustrated in FIGS. 2 and 4.Alternatively or additionally, the hardware information 304 includesinformation describing one or more output mechanisms of the clientdevice 102, such as the display device 110.

In implementations where the client device 102 is communicativelycoupled to a different computing device, the hardware information 304describes a hardware configuration of the different device, one or moreinput mechanisms connected to the different computing device, and one ormore output mechanisms connected to the different computing device. Forinstance, the hardware information 304 may describe a hardwareconfiguration of both client devices 702 and 704, along with theirrespective processing systems 718 and 722, cameras 706 and 712, audiosensors 708 and 714, and display devices 710 and 716, as described aboveand illustrated in FIG. 7.

Step 802 determines a shell state of the client device. The shell statemodule 126, for instance, determines shell information 306 thatdescribes software and firmware installed on the client device 102. Forinstance, the shell information 306 includes information that describesthe installed and available versions of the operating system 104, alongwith installed and available operating system components 104 a-104 c, asdescribed above and illustrated with respect to FIG. 2. Likewise, theshell information 306 includes information describing current andavailable versions of the applications 106, along with anyinterchangeable components associated with the applications 106.Alternatively or additionally, the shell information 306 includesinformation describing current and available versions of the outputmodule 112, its associated components 112 a-112 c, the input module 114,and its associated components 114 a-114 c.

In implementations where the client device 102 is communicativelycoupled to a different computing device, the shell information 306describes a shell state of the client device 102 and the differentdevice, such as respective operating systems 720 and 724 of clientdevices 702 and 704, as described above and illustrated with respect toFIG. 7.

Step 804 determines a context state of the client device. The contextstate module 128, for instance, determines context information 308 thatdescribes the client device 102 in relation to a user of the device andhow the user is using the device. For instance, the context state of theclient device 102 can be described by data or signals associated withone or more of a user's grip on the device, a relative position of thedevice, sound, behavioral data, Hall Effect, user settings, visual data,external connections, and so forth. This is not an exhaustive list, andis only representative of various information that can be used todescribe a context state of the client device 102, as described herein.

For example, the context information 308 may describe whether an adultuser 406 or child user 410 is interacting with the client device 102, asdescribed above and illustrated in FIG. 4. Alternatively oradditionally, the context information 308 may specify whether a singleuser or multiple users are simultaneously interacting with the clientdevice 102, as described above and illustrated in FIG. 5. Alternativelyor additionally, the context information 308 may describe a currentposture of the client device 102, as described above and illustrated inFIG. 6.

Step 806 generates a configuration output based on one or more of thehardware state, the shell state, or the context state of the clientdevice. The component system 122, for instance, generates configurationoutput 310 as described above and illustrated in FIG. 3. Theconfiguration output 310 specifies a subset of client device components,such as a subset of the components illustrated in FIGS. 2 and 7 to beused in performing functionality of the client device 102.

Step 808 configures the client device based on the configuration output.The component system 122, for instance, applies configuration data fromthe configuration output 310 to enable and/or disable various componentsof the client device 102. For instance, the component system 122 usesthe configuration output 310 to activate a specific subset of clientdevice components to dynamically configure the client device 102 basedon a current state of the device.

Thus, FIG. 8 describes a general procedure for generating an output thatconfigures device components based on one or more of a hardware state, ashell state, or a context state of the client device. Inimplementations, the operations of FIG. 8 can be performed by acomputing device implementing the component system 122, such as theclient device 102 of FIG. 1.

FIG. 9 is a flow diagram that describes steps in an example method forconfiguring a client device based on a detected state change inaccordance with one or more implementations. In at least oneimplementation, the flow diagram of FIG. 9 represents a way ofperforming step 806 of FIG. 8.

Step 900 detects a change to at least one of a hardware state, a shellstate, or a context state of a client device. The hardware state module124, for instance, may determine a hardware state of the client device,as described in step 800 of FIG. 8, and store information describingthis hardware state, such as in memory/storage 116 as illustrated inFIG. 1. Thereafter, the hardware state module 124 may continue tomonitor the hardware state of the client device and compare themonitored hardware state to the stored information to determine when achange in hardware state occurs. For instance, the hardware state module124 may monitor the client device to determine whether mouse andkeyboard input mechanisms 408 are currently connected to the clientdevice 102, as described above and illustrated in FIG. 4. Alternativelyor additionally, the hardware state module 124 may monitor the clientdevice 702 to determine that processing systems 718 and 722, cameras 706and 712, audio sensors 708 and 714, and display devices 710 and 716 areavailable to the client device 702 upon establishing a connection withclient device 704, as described above and illustrated in FIG. 7.

Similarly, the shell state module 126 may determine a shell state of theclient device, as described in step 802 of FIG. 8, and store informationdescribing this shell state, such as in memory/storage 116 asillustrated in FIG. 1. Thereafter, the shell state module 126 maycontinue to monitor the shell state of the client device and compare themonitored shell state to the stored information to determine when achange in shell state occurs. For instance, the shell state module 126may monitor the client device 702 to determine that both operatingsystem components 720 a and 724 a are available to the client deviceupon establishing a connection with client device 704, as describedabove and illustrated in FIG. 7.

Further, the context state module 128 may determine a context state ofthe client device, as described in step 804 of FIG. 8, and storeinformation describing the context state, such as in memory/storage 116as illustrated in FIG. 1. Thereafter, the context state module 128continues to monitor the context state of the client device and comparesthe monitored context state to the stored information to determine whena change in context state occurs. For instance, the context state module128 may detect a change in context state when a child user 410 interactswith a client device 102 that was previously interacted with by an adultuser 406, as described and illustrated with respect to FIG. 4.Alternatively or additionally, the context state module 128 may detect achange in context state when an additional user begins to interact withthe client device 102, as described and illustrated with respect to FIG.5. As another example, the context state module 128 may detect a changein context state when the client device 102 transitions from a firstposture to a second posture, as described and illustrated with respectto FIG. 6.

Step 902 configures the client device by activating or deactivating atleast one client device component based on the detected change in state.The component system 122, for instance, may activate one or more clientdevice components and/or deactivate one or more different client devicecomponents illustrated in FIGS. 2 and 7 in response to detecting achange in one or more of a hardware state, shell state, or context stateof the client device 102. The one or more client device components to beactivated and/or deactivated in response to the detected state changemay be specified in the configuration output 310, as illustrated in FIG.3. Thus, by activating or deactivating individual client devicecomponents, the component system 122 is configured to adapt the clientdevice 102 to dynamically adjust to state changes. For instance, thecomponent system 122 can adapt the client device between configurations402 and 404 of FIG. 4, between configurations 502 and 504 of FIG. 5,between configurations 602 and 604 of FIG. 6, between configurations 702and 704 of FIG. 7, and so on.

FIG. 10 is a flow diagram that describes steps in a method for causingan application to execute at a client device using a subset of clientdevice components in accordance with one or more implementations. In atleast one implementation, the flow diagram of FIG. 10 represents a wayof performing step 806 of FIG. 8.

Step 1000 receives a request for an application to execute at a clientdevice. The component system 122, for instance, detects that anapplication 106 is requesting to execute at the client device 102. Inaccordance with one or more implementations, step 1000 is performed inresponse to receiving user input at the client device 102 that commencesexecution of the application 106, such as via user input received fromone or more input mechanisms 202 as illustrated in FIG. 2.

Step 1002 determines a set of client device components that are useableto configure the client device. The component system 122, for instance,analyzes the operating system 104, the applications 106, thecommunication module 108, the output module 112, and the input module114 to identify interchangeable components that are associated witheach, such as components 104 a-104 c, 112 a-112 c, and 114 a-114 c, asillustrated in FIG. 2. By analyzing the output module 112 and the inputmodule 114, the component system is additionally configured to identifyoutput devices and input devices that are available for use by theclient device 102, such as the display device 110, the digitizer 204,sensors 206 and sensor components 206 a-206 c, touch input devices 208,and analog input devices 210, as illustrated in FIGS. 1 and 2.Alternatively or additionally, the set of client device components thatare useable to configure the client device represents client devicecomponents implemented across multiple connected client devices, such asthe components of client devices 702 and 704, as illustrated in FIG. 7.

Step 1004 selects a subset of the available client device components.The component system 122, for instance, determines a current hardwarestate, current shell state, and current context state of the clientdevice 102, as described with respect to steps 800-804 of FIG. 8. Basedon one or more of the hardware state, shell state, or context state ofthe client device, the component system selects one or more clientdevice components for use in configuring the client device 102 anddesignates the one or more client device components as the subset of theavailable client device components. In some implementations, the subsetof client device components represents a change in a number of clientdevice components running in parallel in comparison to a previous numberof client device components running in parallel on the client device102.

Step 1006 causes the application to execute at the client device usingthe subset of client device components. The component system 122, forexample, generates a configuration output 310 and communicates theconfiguration output 310 to the application 106 in a manner thatrepresents the client device 102 as comprising the subset of clientdevice components. In some implementations, the configuration output 310is generated such that the client device 106 is represented to theapplication 106 as consisting of the subset of client device components.For instance, in the illustrated example of FIG. 7, the configurationoutput 310 can be generated such that the connected client devices 702and 704 are represented to application 106 as a single client device102. In this manner, the component system 122 can dictate how the clientdevice 102 is represented to the application 106 and thus control a userexperience of the application without requiring modification ofunderlying application code. Further, the component system 122 can forcedifferent applications 106 to behave in a consistent manner, even ifdifferent applications are designed to leverage different hardwarefunctionalities.

Thus, the component system 122 causes applications to execute at theclient device 102 in a particular manner by representing the clientdevice as a subset of client device components, in order to adapt userexperiences of the respective applications to hardware, shell, andcontext states of the client device. Thus, the component system 122causes applications to dynamically adapt to client device state changes,in a manner that does not require application developers to designapplications to account for variations in device hardware, shell, orcontext states.

Having described some example implementation details, consider now adiscussion of an example system and device in accordance with one ormore implementations.

FIG. 11 illustrates an example system generally at 1100 that includes anexample computing device 1102 that is representative of one or morecomputing systems and/or devices that may implement various techniquesdescribed herein. For example, the client device 102 discussed abovewith reference to FIG. 1 can be embodied as the computing device 1102.The computing device 1102 may be, for example, a server of a serviceprovider, a device associated with the client (e.g., a client device),an on-chip system, and/or any other suitable computing device orcomputing system.

The example computing device 1102 as illustrated includes a processingsystem 1104, one or more computer-readable media 1106, and one or moreInput/Output (I/O) Interfaces 1108 that are communicatively coupled, oneto another. Although not shown, the computing device 1102 may furtherinclude a system bus or other data and command transfer system thatcouples the various components, one to another. A system bus can includeany one or combination of different bus structures, such as a memory busor memory controller, a peripheral bus, a universal serial bus, and/or aprocessor or local bus that utilizes any of a variety of busarchitectures. A variety of other examples are also contemplated, suchas control and data lines.

The processing system 1104 is representative of functionality to performone or more operations using hardware. Accordingly, the processingsystem 1104 is illustrated as including hardware element 1110 that maybe configured as processors, functional blocks, and so forth. This mayinclude implementation in hardware as an application specific integratedcircuit or other logic device formed using one or more semiconductors.The hardware elements 1110 are not limited by the materials from whichthey are formed or the processing mechanisms employed therein. Forexample, processors may be comprised of semiconductor(s) and/ortransistors (e.g., electronic integrated circuits (ICs)). In such acontext, processor-executable instructions may beelectronically-executable instructions.

The computer-readable media 1106 is illustrated as includingmemory/storage 1112. The memory/storage 1112 represents memory/storagecapacity associated with one or more computer-readable media. Thememory/storage 1112 may include volatile media (such as random accessmemory (RAM)) and/or nonvolatile media (such as read only memory (ROM),Flash memory, optical disks, magnetic disks, and so forth). Thememory/storage 1112 may include fixed media (e.g., RAM, ROM, a fixedhard drive, and so on) as well as removable media (e.g., Flash memory, aremovable hard drive, an optical disc, and so forth). Thecomputer-readable media 1106 may be configured in a variety of otherways as further described below.

Input/output interface(s) 1108 are representative of functionality toallow a user to enter commands and information to computing device 1102,and also allow information to be presented to the user and/or othercomponents or devices using various input/output devices. Examples ofinput devices include a keyboard, a cursor control device (e.g., amouse), a microphone (e.g., for voice recognition and/or spoken input),a scanner, touch functionality (e.g., capacitive or other sensors thatare configured to detect physical touch), motion functionality (e.g.,accelerometers or other sensors that are configured to detect physicalmotion), a camera (e.g., which may employ visible or non-visiblewavelengths such as infrared frequencies to detect movement that doesnot involve touch as gestures), six degrees of freedom controllers suchas used in virtual reality and augmented reality technologies, and soforth. Examples of output devices include a display device (e.g., amonitor or projector), speakers, a printer, a network card,tactile-response device, head mounted displays (e.g., for virtualreality and augmented reality applications), and so forth. Thus, thecomputing device 1102 may be configured in a variety of ways as furtherdescribed below to support user interaction.

Various techniques may be described herein in the general context ofsoftware, hardware elements, or program modules. Generally, such modulesinclude routines, programs, objects, elements, components, datastructures, and so forth that perform particular tasks or implementparticular abstract data types. The terms “module,” “functionality,”“entity,” and “component” as used herein generally represent software,firmware, hardware, or a combination thereof. The features of techniquesdescribed herein are platform-independent, meaning that the techniquesmay be implemented on a variety of commercial computing platforms havinga variety of processors.

An implementation of the described modules and techniques may be storedon or transmitted across some form of computer-readable media. Thecomputer-readable media may include a variety of media that may beaccessed by the computing device 1102. By way of example, and notlimitation, computer-readable media may include “computer-readablestorage media” and “computer-readable signal media.”

“Computer-readable storage media” may refer to media and/or devices thatenable persistent storage of information in contrast to mere signaltransmission, carrier waves, or signals per se. Computer-readablestorage media do not include signals per se. The computer-readablestorage media includes hardware such as volatile and non-volatile,removable and non-removable media and/or storage devices implemented ina method or technology suitable for storage of information such ascomputer readable instructions, data structures, program modules, logicelements/circuits, or other data. Examples of computer-readable storagemedia may include, but are not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical storage, hard disks, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or otherstorage device, tangible media, or article of manufacture suitable tostore the desired information and which may be accessed by a computer.

“Computer-readable signal media” may refer to a signal-bearing mediumthat is configured to transmit instructions to the hardware of thecomputing device 1102, such as via a network. Signal media typically mayembody computer readable instructions, data structures, program modules,or other data in a modulated data signal, such as carrier waves, datasignals, or other transport mechanism. Signal media also include anyinformation delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media include wired media such as awired network or direct-wired connection, and wireless media such asacoustic, radio frequency (RF), infrared, and other wireless media.

As previously described, hardware elements 1110 and computer-readablemedia 1106 are representative of instructions, modules, programmabledevice logic and/or fixed device logic implemented in a hardware formthat may be employed in some implementations to implement at least someaspects of techniques described herein. Hardware elements may includecomponents of an integrated circuit or on-chip system, anapplication-specific integrated circuit (ASIC), a field-programmablegate array (FPGA), a complex programmable logic device (CPLD), and otherimplementations in silicon or other hardware devices. In this context, ahardware element may operate as a processing device that performsprogram tasks defined by instructions, modules, and/or logic embodied bythe hardware element as well as a hardware device utilized to storeinstructions for execution, e.g., the computer-readable storage mediadescribed previously.

Combinations of the foregoing may also be employed to implement varioustechniques and modules described herein. Accordingly, software,hardware, or program modules and other program modules may beimplemented as one or more instructions and/or logic embodied on someform of computer-readable storage media and/or by one or more hardwareelements 1110. The computing device 1102 may be configured to implementparticular instructions and/or functions corresponding to the softwareand/or hardware modules. Accordingly, implementation of modules that areexecutable by the computing device 1102 as software may be achieved atleast partially in hardware, e.g., through use of computer-readablestorage media and/or hardware elements 1110 of the processing system.The instructions and/or functions may be executable/operable by one ormore articles of manufacture (for example, one or more computing devices1102 and/or processing systems 1104) to implement techniques, modules,and examples described herein.

As further illustrated in FIG. 11, the example system 1100 enablesubiquitous environments for a seamless user experience when runningapplications on a personal computer (PC), a television device, and/or amobile device. Services and applications run substantially similar inall three environments for a common user experience when transitioningfrom one device to the next while utilizing an application, playing avideo game, watching a video, and so on.

In the example system 1100, multiple devices are interconnected througha central computing device. The central computing device may be local tothe multiple devices or may be located remotely from the multipledevices. In one embodiment, the central computing device may be a cloudof one or more server computers that are connected to the multipledevices through a network, the Internet, or other data communicationlink.

In one embodiment, this interconnection architecture enablesfunctionality to be delivered across multiple devices to provide acommon and seamless experience to a user of the multiple devices. Eachof the multiple devices may have different physical requirements andcapabilities, and the central computing device uses a platform to enablethe delivery of an experience to the device that is both tailored to thedevice and yet common to all devices. In one embodiment, a class oftarget devices is created and experiences are tailored to the genericclass of devices. A class of devices may be defined by physicalfeatures, types of usage, or other common characteristics of thedevices.

In various implementations, the computing device 1102 may assume avariety of different configurations, such as for computer 1114, mobile1116, and television 1118 uses. Each of these configurations includesdevices that may have generally different constructs and capabilities,and thus the computing device 1102 may be configured according to one ormore of the different device classes. For instance, the computing device1102 may be implemented as the computer 1114 class of a device thatincludes a personal computer, desktop computer, a multi-screen computer,laptop computer, netbook, and so on.

The computing device 1102 may also be implemented as the mobile 1116class of device that includes mobile devices, such as a mobile phone,portable music player, portable gaming device, a tablet computer, awearable device (e.g., a watch, glasses, an article of clothing, etc.),a multi-screen computer, and so on. The computing device 1102 may alsobe implemented as the television 1118 class of device that includesdevices having or connected to generally larger screens in casualviewing environments. These devices include televisions, set-top boxes,gaming consoles, and so on.

Techniques described herein may be supported by these variousconfigurations of the computing device 1102 and are not limited to thespecific examples of techniques described herein. For example,functionalities discussed with reference to the client device 102 may beimplemented all or in part through use of a distributed system, such asover a “cloud” 1120 via a platform 1122 as described below.

The cloud 1120 includes and/or is representative of a platform 1122 forresources 1124. The platform 1122 abstracts underlying functionality ofhardware (e.g., servers) and software resources of the cloud 1120. Theresources 1124 may include applications and/or data that can be utilizedwhile computer processing is executed on servers that are remote fromthe computing device 1102. Resources 1124 can also include servicesprovided over the Internet and/or through a subscriber network, such asa cellular or Wi-Fi network.

The platform 1122 may abstract resources and functions to connect thecomputing device 1102 with other computing devices. The platform 1122may also serve to abstract scaling of resources to provide acorresponding level of scale to encountered demand for the resources1124 that are implemented via the platform 1122. Accordingly, in aninterconnected device embodiment, implementation of functionalitydescribed herein may be distributed throughout the system 1100. Forexample, the functionality may be implemented in part on the computingdevice 1102 as well as via the platform 1122 that abstracts thefunctionality of the cloud 1120.

Discussed herein are a number of methods that may be implemented toperform techniques discussed herein. Aspects of the methods may beimplemented in hardware, firmware, or software, or a combinationthereof. The methods are shown as a set of steps that specify operationsperformed by one or more devices and are not necessarily limited to theorders shown for performing the operations by the respective blocks.Further, an operation shown with respect to a particular method may becombined and/or interchanged with an operation of a different method inaccordance with one or more implementations. Aspects of the methods canbe implemented via interaction between various entities discussed abovewith reference to the environment 100.

In the discussions herein, various different implementations aredescribed. It is to be appreciated and understood that eachimplementation described herein can be used on its own or in connectionwith one or more other implementations described herein. Further aspectsof techniques discussed herein relate to one or more of the followingimplementations:

A system for configuring a client device based on a configuration outputthat specifies an interchangeable component to be activated, the systemcomprising: at least one processor; and one or more computer-readablestorage media including instructions stored thereon that, responsive toexecution by the at least one processor, cause the system to performoperations including: determining a hardware state of a client devicebased on hardware information describing at least one hardware mechanismof the client device; determining a shell state of the client devicebased on shell information describing an operating system installed onthe client device; determining a context state of the client devicebased on context information describing a current context of the atleast one hardware mechanism and a current context of the operatingsystem, relative to a user or a surrounding environment of the clientdevice; generating a configuration output that specifies at least oneinterchangeable component to be activated by the client device, based onthe hardware state, the shell state, and the context state of the clientdevice; and configuring the client device based on the configurationoutput.

In addition to any of the above described systems, any one orcombination of: wherein the at least one hardware mechanism includes aninput mechanism of the client device and the hardware informationdescribes one or more interchangeable components that are available toconfigure functionality of the input mechanism; wherein the at least onehardware mechanism includes an output mechanism of the client device andthe hardware information describes one or more interchangeablecomponents that are available to configure functionality of the outputmechanism; wherein the shell information describes one or moreinterchangeable components that are available to configure functionalitythe operating system; wherein the context information describes at leastone of the user's grip on the client device, a position of the clientdevice relative to the user or the surrounding environment, a soundreceived by the client device, user profile information for the user, aposture of the client device, visual information received by the clientdevice, a connection between the client device and an external device,or a number of users interacting with the client device; wherein the atleast one interchangeable component includes a subset of interchangeablecomponents available to the client device and the output causes theclient device to perform operations using the subset of interchangeablecomponents; and wherein the at least one interchangeable componentincludes a subset of interchangeable components available to anapplication executing on the client device and the output causes theapplication to execute on the client device using the subset ofinterchangeable components.

A computer-implemented method for configuring a client device to performan operation using a subset of interchangeable components, thecomputer-implemented method comprising: detecting at least one of achange to a hardware state of a client device based on a change inavailable hardware mechanisms, a change to a shell state of the clientdevice based on a change in version to an operating system or anapplication on the client device, or a change to a context state of theclient device based on a change in how the client device is being usedrelative to a surrounding environment; and responsive to detecting thechange, configuring the client device by selecting a subset ofinterchangeable components that are available to the client device,activating the subset of interchangeable components, and causing theclient device to perform operations using the subset of interchangeablecomponents.

In addition to any of the above described methods, any one orcombination of: wherein detecting the change to the hardware state ofthe client device comprises detecting that the client device connects toan external device, and configuring the client device comprises enablingthe client device to perform operations using one or more hardwaremechanisms of the external device; wherein detecting the change to thehardware state of the client device comprises detecting that the clientdevice connects to an external device, the operations further comprisingdetermining a set of interchangeable components that are installed onthe client device, determining a set of interchangeable components thatare installed on the external device, and the subset of interchangeablecomponents includes interchangeable components from the set installed onthe client device and from the set installed on the external device;wherein detecting the change to the hardware state of the client devicecomprises detecting that the client device is connected to a car,detecting the change to the context state of the client device comprisesdetecting that the client device and the car are moving, and configuringthe client device comprises disabling a display of the client device byomitting an interchangeable component for the display from the subset ofinterchangeable components; wherein detecting the change to the contextstate of the client device comprises detecting an increase in a numberof users interacting with the client device, the operations furthercomprising generating a duplicate instance of each interchangeablecomponent in the subset of interchangeable components and outputtingmultiple user experiences, the multiple user experiences including auser experience for each of the number of users interacting with theclient device; wherein detecting the change to the context state of theclient device comprises detecting a change in posture of the clientdevice and a number of interchangeable components included in the subsetof interchangeable components is different from a number ofinterchangeable components that were active prior to the change inposture of the client device; wherein detecting the change to thecontext state of the client device includes determining that a user ofthe client device has accessibility needs and the subset ofinterchangeable components are selected to accommodate the accessibilityneeds; and wherein detecting the change and configuring the clientdevice are performed during runtime at the client device and the subsetof interchangeable components are configured to be run concurrently bythe client device.

A computer-implemented method for configuring a client device to beexecutable using a subset of components, the computer-implemented methodcomprising: receiving a request for an application to execute at aclient device; determining a set of client device components that areuseable to configure functionality of the client device in response toreceiving the request; selecting a subset of components from the set ofclient device components based on one or more of a hardware state of theclient device describing at least one hardware mechanism of the clientdevice, a shell state of the client device describing the applicationand an operating system installed on the client device, or a contextstate of the client device describing a current context of the at leastone hardware mechanism, the application, and the operating system,relative to a user or a surrounding environment of the client device;and causing the application to execute at the client device using thesubset of components.

In addition to any of the above described methods, any one orcombination of: wherein the subset of components omits at least onecomponent from the set of client device components that is available foruse by the client device; wherein a device type of the client device isa first device type, the application is designed to provide a first userexperience for the first device type and a different user experience fora second device type, the subset of components represents the clientdevice as the second type, and causing the application to execute at theclient device comprises causing the application to provide the differentuser experience; wherein the at least one hardware mechanism includes atleast one output mechanism of the client device and the hardware stateof the client device includes information describing one or moreinterchangeable components that are available to configure functionalityof the at least one output mechanism; and wherein the current context ofthe at least one hardware mechanism, the application, and the operatingsystem is determined based on at least one of a user's grip on theclient device, a relative position of the client device, a soundreceived by the client device, user profile information for the user, aposture of the client device, visual information received by the clientdevice, a connection between the client device and an external device,or a number of users interacting with the client device.

What is claimed is:
 1. A computer-implemented method comprising:determining that a computer system of a vehicle has paired with a clientdevice during runtime of the client device; in response to determiningthat the computer system of the vehicle has paired with the clientdevice, executing processing operations that comprise: determining ahardware state of the client device based on evaluation of hardwareinformation describing at least one hardware mechanism of the clientdevice; determining a context state of the client device indicating acurrent state of application components for the client device and thecomputer system of the vehicle; generating a configuration output thatspecifies an operation state of a subset of the application componentsbased on the hardware state of the client device and the context stateof the client device; and configuring the client device to modify theoperation state of the subset of application components based on anevaluation of the configuration output and the computer system of thevehicle being paired with the client device.
 2. The computer-implementedmethod as recited in claim 1, wherein the processing operations,executed in response to determining that the computer system of thevehicle has paired with the client device, further comprise: determininga shell state of the client device based on evaluation of shellinformation describing a state of software of the application or servicethat is installed on the client device, and wherein the generating ofthe configuration output occurs based on evaluation of the hardwarestate of the client device, the shell state of the client device and thecontext state of the client device.
 3. The computer-implemented methodas recited in claim 1, wherein the determining that the computer-systemof the vehicle has paired with the client device comprises detectingthat an external device is connected with the client device.
 4. Thecomputer-implemented method as recited in claim 1, wherein theprocessing operations, executed in response to determining that thecomputer system of the vehicle has paired with the client device,further comprise: receiving, from the computer system of the vehicle, anindication that the vehicle is in motion, and wherein the configuring ofthe client device to modify the operation state of the subset ofapplication components occurs based on the configuration output, and theindication that the vehicle is in motion.
 5. The computer-implementedmethod as recited in claim 3, wherein the external device comprises oneor more display devices, and wherein the detecting that the externaldevice is connected with the client device comprises detecting that theone or more display devices is connected with the client device.
 6. Asystem comprising: at least one processor; and one or morecomputer-readable storage media including instructions stored thereonthat, responsive to execution by the at least one processor, cause thesystem to perform processing operations that comprise: determining atype of change in usage of one or more external devices comprising oneor more display devices, connected with a client device comprising anintegrated display, during runtime of the client device, wherein thedetermining comprises detecting an activation of the one or more displaydevices connected with the client device, in response to determining thetype of change in usage of the one or more external devices, executingprocessing operations that comprise: determining a hardware state of theclient device based on evaluation of hardware information describing atleast one hardware mechanism of the client device, determining a contextstate of the client device indicating a current state of applicationcomponents for the client device and the one or more external devices,generating a configuration output that specifies an operation state of asubset of the application components based on the hardware state of theclient device and the context state of the client device, andconfiguring the client device to modify the operation state of thesubset of application components based on an evaluation of theconfiguration output and the type of change in usage of the one or moreexternal devices.
 7. The system as recited in claim 6, wherein theprocessing operations, executed by the at least one processor, furthercomprise: determining a shell state of the client device based onevaluation of shell information describing a state of software of theapplication or service that is installed on the client device, andwherein the generating of the configuration output occurs based onevaluation of the hardware state of the client device, the shell stateof the client device and the context state of the client device.
 8. Thesystem as recited in claim 6, wherein the determining of the type ofchange in usage of the one or more external devices comprises detectingthat an external device is connected with the client device.
 9. Thesystem as recited in claim 8, wherein the external device is a computersystem of a vehicle, and wherein the detecting that the one or moreexternal devices is connected with the client device comprises detectingthat the computer system of the vehicle pairs with the client device.10. The system as recited in claim 9, wherein the processing operations,executed by the at least one processor, further comprise: receiving,from the computer system of the vehicle, an indication that the vehicleis in motion, and wherein the configuring of the client device to modifythe operation state of the subset of application components occurs basedon the configuration output, the type of change in usage of the one ormore external devices and the indication that the vehicle is in motion.11. The system as recited in claim 8, wherein the detecting that the oneor more external devices is connected with the client device furthercomprises detecting that the one or more display devices is connectedwith the client device.
 12. The system as recited in claim 6, whereinthe determining of the type of change in usage of the one or moreexternal devices further comprises detecting a change in positioning ofthe one or more display devices.
 13. The system as recited in claim 12,wherein the generating of the configuration output that specifies theoperation state of the subset of the application components comprisesidentification of a primary display from a display device of the one ormore display devices, and wherein a modification of the operation stateof the subset of application components changes the display device to asecondary display based on evaluation of the configuration output andthe type of change in usage of the one or more external devices.
 14. Acomputer-implemented method comprising: detecting a type of user actionthat affects usage of a sensor of a client device during runtime of theclient device; in response to determining the user action that affectsusage of the sensor of the client device, executing processingoperations that comprise: determining a hardware state of the clientdevice based on evaluation of hardware information describing at leastone hardware mechanism of the client device, determining a shell stateof the client device based on evaluation of shell information describinga state of software of an application, operating system, or service thatis installed on the client device; determining a context state of theclient device indicating a current state of application components forthe client device and the one or more external devices, generating aconfiguration output that specifies an operation state of a subset ofthe application components based on the hardware state of the clientdevice, the shell state of the client device, and the context state ofthe client device, and configuring the client device to modify theoperation state of the subset of application components based on anevaluation of the configuration output and the type of user action thataffects usage of the sensor of the client device.
 15. Thecomputer-implemented method as recited in claim 14, wherein the sensorof the client device is a camera sensor of the client device, whereinthe detecting of the type of user action that affects usage of thesensor of the client device comprises a user covering the camera sensorof the client device, and wherein the configuring of the client deviceto modify the operation state of the subset of application componentscomprises de-activating the camera sensor.